Understanding the effects of sequence numbers

Server performance and stability problems can result if many number sequences are stored in a vault. The quantity of numbers produced by each sequence has no affect on performance or stability. You can define any number of custom number sequences in Meridian Enterprise using methods like NextSequenceNumber. Each number sequence can be accessed by name and produces one series of numbers that can be used in automatically generated document names and similar purposes.

When many number sequences are defined in one database, much information needs to be stored in the database (method of numbering, current number, numbering formula, and so on). This is true for all types of databases, not just Meridian Enterprise and is a logical result of using sequences in general. Using more than approximately 500 number sequences should be avoided. If more number sequences are necessary, other solutions are often possible by reviewing the system design. For example, it may be possible to use a single custom property with 500 values and one sequence number, rather than 500 sequence numbers.

When solutions to reduce the quantity of number sequences are not practical, alternatives that will not affect performance include:

• Store the number sequences in their own vault
• Store the number sequences in an external database table.

For information on using number sequences with VBScript, see the BlueCielo Meridian Enterprise Configuration Guide . For information on using number sequences with the Meridian API, see the BlueCielo Meridian Enterprise Developer's Guide.